Declarative iot data control

ABSTRACT

The disclosed technology is generally directed to communications in an IoT environment. For example, such technology is usable for IoT data control. In one example of the technology, a declarative data request is received. The declarative data request is a request for data from multiple IoT devices. The declarative data request is translated into a plurality of individual requests. Destination IoT devices associated with the plurality of individual requests are identified. The plurality of individual requests to the destination IoT devices are sent. IoT data is received from the destination IoT devices based on the plurality of individual requests. The declarative data request is responded to based on the received IoT data.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to U.S. Provisional Pat. App. No.62/434,888, filed Dec. 15, 2016, entitled “DECLARATIVE IOT DATA CONTROL”(Atty. Dkt. No. 400622-US-PSP). The entirety of this afore-mentionedapplication is incorporated herein by reference.

BACKGROUND

The Internet of Things (“IoT”) generally refers to a system of devicescapable of communicating over a network. The devices can includeeveryday objects such as toasters, coffee machines, thermostat systems,washers, dryers, lamps, automobiles, and the like. The devices can alsoinclude sensors in buildings and factory machines, sensors and actuatorsin remote industrial systems, and the like. The network communicationscan be used for device automation, data capture, providing alerts,personalization of settings, and numerous other applications.

SUMMARY OF THE DISCLOSURE

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

Briefly stated, the disclosed technology is generally directed tocommunications in an IoT environment. For example, such technology isusable for IoT data control. In one example of the technology, adeclarative data request is received. The declarative data request is arequest for data from multiple IoT devices. The declarative data requestis translated into a plurality of individual requests. Destination IoTdevices associated with the plurality of individual requests areidentified. The plurality of individual requests to the destination IoTdevices are sent. IoT data is received from the destination IoT devicesbased on the plurality of individual requests. The declarative datarequest is responded to based on the received IoT data.

Examples of the disclosure provide on-demand telemetry via a declarativeIoT telemetry request. Examples of the disclosure decouple IoT deviceapplications from IoT solution back-ends, for example, with respect tomanagement of telemetry data. In this way, via declarative IoT telemetryrequests, the IoT devices may be used, so that, in some examples, theapplication back-end does not require different solution-specific codeor alteration of functional design depending on the type of IoT databeing requested—instead, the request from the application back-end maybe de-coupled from the manner in which the request is answered.

Other aspects of and applications for the disclosed technology will beappreciated upon reading and understanding the attached figures anddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples of the present disclosure aredescribed with reference to the following drawings. In the drawings,like reference numerals refer to like parts throughout the variousfigures unless otherwise specified. These drawings are not necessarilydrawn to scale.

For a better understanding of the present disclosure, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating one example of a suitableenvironment in which aspects of the technology may be employed;

FIG. 2 is a block diagram illustrating one example of a suitablecomputing device according to aspects of the disclosed technology;

FIG. 3 is a block diagram illustrating an example of a system for IoTdata control;

FIG. 4 is a diagram illustrating an example dataflow for a process forIoT data control; and

FIG. 5 is a block diagram illustrating an example of the system for IoTdata control of FIG. 3, in accordance with aspects of the presentdisclosure.

DETAILED DESCRIPTION

The following description provides specific details for a thoroughunderstanding of, and enabling description for, various examples of thetechnology. One skilled in the art will understand that the technologymay be practiced without many of these details. In some instances,well-known structures and functions have not been shown or described indetail to avoid unnecessarily obscuring the description of examples ofthe technology. It is intended that the terminology used in thisdisclosure be interpreted in its broadest reasonable manner, even thoughit is being used in conjunction with a detailed description of certainexamples of the technology. Although certain terms may be emphasizedbelow, any terminology intended to be interpreted in any restrictedmanner will be overtly and specifically defined as such in this DetailedDescription section. Throughout the specification and claims, thefollowing terms take at least the meanings explicitly associated herein,unless the context dictates otherwise. The meanings identified below donot necessarily limit the terms, but merely provide illustrativeexamples for the terms. For example, each of the terms “based on” and“based upon” is not exclusive, and is equivalent to the term “based, atleast in part, on”, and includes the option of being based on additionalfactors, some of which may not be described herein. As another example,the term “via” is not exclusive, and is equivalent to the term “via, atleast in part”, and includes the option of being via additional factors,some of which may not be described herein. The meaning of “in” includes“in” and “on.” The phrase “in one embodiment,” or “in one example,” asused herein does not necessarily refer to the same embodiment orexample, although it may. Use of particular textual numeric designatorsdoes not imply the existence of lesser-valued numerical designators. Forexample, reciting “a widget selected from the group consisting of athird foo and a fourth bar” would not itself imply that there are atleast three foo, nor that there are at least four bar, elements.References in the singular are made merely for clarity of reading andinclude plural references unless plural references are specificallyexcluded. The term “or” is an inclusive “or” operator unlessspecifically indicated otherwise. For example, the phrases “A or B”means “A, B, or A and B.” As used herein, the terms “component” and“system” are intended to encompass hardware, software, or variouscombinations of hardware and software. Thus, for example, a system orcomponent may be a process, a process executing on a computing device,the computing device, or a portion thereof. IoT data refers to datacollected by and/or stored in IoT devices, including telemetry data andother types of data. A declarative request or declarative query is arequest or query that is referentially transparent, meaning that therequest is unchanged irrespective of whether any term used in therequest is a reference or an actual value that the reference is pointingto. In essence, a declarative query specifies what information is beingrequested but does not specify how the query is to be answered.

Briefly stated, the disclosed technology is generally directed tocommunications in an IoT environment. For example, such technology isusable for IoT data control. In one example of the technology, adeclarative data request is received. The declarative data request is arequest for data from multiple IoT devices. The declarative data requestis translated into a plurality of individual requests. Destination IoTdevices associated with the plurality of individual requests areidentified. The plurality of individual requests to the destination IoTdevices are sent. IoT data is received from the destination IoT devicesbased on the plurality of individual requests. The declarative datarequest is responded to based on the received IoT data.

Examples of the disclosure decouple IoT device applications from IoTsolution back-ends, for example, with respect to management of telemetrydata. In this way, via declarative IoT requests, the IoT devices may beused, so that, in some examples, the IoT device code does not requirefunctional changes, application back-end does not require differentsolution-specific code or alteration of functional design, and/or thelike, depending on the type of IoT data being requested. Instead, therequest from the application back-end may be de-coupled from the mannerin which the request is answered. Examples of the disclosure provideon-demand telemetry via a declarative IoT telemetry request. An IoTtelemetry request can be made and responded to as if all the devicetelemetry from all of the IoT devices are available, as if all of theIoT devices were part of a large distributed database, even if the IoTdevices include heterogeneous sets of devices, consisting of differentdevices, or different revisions or configurations of the same class ofdevices, including different firmware and/or software on IoT devices.

Via declarative IoT control, the IoT devices may send telemetry to thecloud with no special buffering and/or batching being considered bydevice applications. Device applications may expose all availabletelemetry streams without considering the back-end of the IoT solution.The cloud back-end may dynamically query the requested telemetry datawith corresponding frequency of sending telemetry data, normalizationdefinition, and destination component. In some examples, the applicationcode on the IoT devices does not have to handle buffering/configurationlogic, and require no changes if the solution's back-end requestsdifferent telemetry streams and/or different frequencies of sendingtelemetry data. Instead, in some examples, a service component may takeresponsibility for answering individual telemetry requests, and forhandling requested buffering/frequency matters. In such examples, therest of the device (including application code) may be unconcerned withbuffering/frequency matters and can simply expose the telemetry data tothe component service.

Illustrative Devices/Operating Environments

FIG. 1 is a diagram of environment 100 in which aspects of thetechnology may be practiced. As shown, environment 100 includescomputing devices 110, as well as network nodes 120, connected vianetwork 130. Even though particular components of environment 100 areshown in FIG. 1, in other examples, environment 100 can also includeadditional and/or different components. For example, in certainexamples, the environment 100 can also include network storage devices,maintenance managers, and/or other suitable components (not shown).Computing devices no shown in FIG. 1 may be in various locations,including on premise, in the cloud, or the like. For example, computerdevices 110 may be on the client side, on the server side, or the like.

As shown in FIG. 1, network 130 can include one or more network nodes120 that interconnect multiple computing devices no, and connectcomputing devices no to external network 140, e.g., the Internet or anintranet. For example, network nodes 120 may include switches, routers,hubs, network controllers, or other network elements. In certainexamples, computing devices no can be organized into racks, actionzones, groups, sets, or other suitable divisions. For example, in theillustrated example, computing devices no are grouped into three hostsets identified individually as first, second, and third host sets 112a-112 c. In the illustrated example, each of host sets 112 a-112 c isoperatively coupled to a corresponding network node 120 a-120 c,respectively, which are commonly referred to as “top-of-rack” or “TOR”network nodes. TOR network nodes 120 a-120 c can then be operativelycoupled to additional network nodes 120 to form a computer network in ahierarchical, flat, mesh, or other suitable types of topology thatallows communications between computing devices no and external network140. In other examples, multiple host sets 112 a-112 c may share asingle network node 120. Computing devices 110 may be virtually any typeof general- or specific-purpose computing device. For example, thesecomputing devices may be user devices such as desktop computers, laptopcomputers, tablet computers, display devices, cameras, printers, orsmartphones. However, in a data center environment, these computingdevices may be server devices such as application server computers,virtual computing host computers, or file server computers. Moreover,computing devices no may be individually configured to providecomputing, storage, and/or other suitable computing services.

In some examples, one or more of the computing devices no is an IoTdevice, a gateway device, a device that comprises part or all of an IoThub, a device comprising part or all of an application back-end, or thelike, as discussed in greater detail below.

Illustrative Computing Device

FIG. 2 is a diagram illustrating one example of computing device 200 inwhich aspects of the technology may be practiced. Computing device 200may be virtually any type of general- or specific-purpose computingdevice. For example, computing device 200 may be a user device such as adesktop computer, a laptop computer, a tablet computer, a displaydevice, a camera, a printer, embedded device, programmable logiccontroller (PLC), or a smartphone. Likewise, computing device 200 mayalso be server device such as an application server computer, a virtualcomputing host computer, or a file server computer, e.g., computingdevice 200 may be an example of computing device 110 or network node 120of FIG. 1. Computing device 200 may also be an IoT device that connectsto a network to receive IoT services. Likewise, computer device 200 maybe an example any of the devices illustrated in or referred to in FIGS.3-5, as discussed in greater detail below. As illustrated in FIG. 2,computing device 200 includes processing circuit 210, operating memory220, memory controller 230, data storage memory 250, input interface260, output interface 270, and network adapter 280. Each of theseafore-listed components of computing device 200 includes at least onehardware element.

Computing device 200 includes at least one processing circuit 210configured to execute instructions, such as instructions forimplementing the herein-described workloads, processes, or technology.Processing circuit 210 may include a microprocessor, a microcontroller,a graphics processor, a coprocessor, a field-programmable gate array, aprogrammable logic device, a signal processor, or any other circuitsuitable for processing data. The aforementioned instructions, alongwith other data (e.g., datasets, metadata, operating systeminstructions, etc.), may be stored in operating memory 220 duringrun-time of computing device 200. Operating memory 220 may also includeany of a variety of data storage devices/components, such as volatilememories, semi-volatile memories, random access memories, staticmemories, caches, buffers, or other media used to store run-timeinformation. In one example, operating memory 220 does not retaininformation when computing device 200 is powered off. Rather, computingdevice 200 may be configured to transfer instructions from anon-volatile data storage component (e.g., data storage component 250)to operating memory 220 as part of a booting or other loading process.

Operating memory 220 may include 4th generation double data rate (DDR4)memory, 3rd generation double data rate (DDR3) memory, other dynamicrandom access memory (DRAM), High Bandwidth Memory (HBM), Hybrid MemoryCube memory, 3D-stacked memory, static random access memory (SRAM), orother memory, and such memory may comprise one or more memory circuitsintegrated onto a DIMM, SIMM, SODIMM, or other packaging. Such operatingmemory modules or devices may be organized according to channels, ranks,and banks. For example, operating memory devices may be coupled toprocessing circuit 210 via memory controller 230 in channels. Oneexample of computing device 200 may include one or two DIMMs perchannel, with one or two ranks per channel. Operating memory within arank may operate with a shared clock, and shared address and commandbus. Also, an operating memory device may be organized into severalbanks where a bank can be thought of as an array addressed by row andcolumn. Based on such an organization of operating memory, physicaladdresses within the operating memory may be referred to by a tuple ofchannel, rank, bank, row, and column.

Despite the above-discussion, operating memory 220 specifically does notinclude or encompass communications media, any communications medium, orany signals per se.

Memory controller 230 is configured to interface processing circuit 210to operating memory 220. For example, memory controller 230 may beconfigured to interface commands, addresses, and data between operatingmemory 220 and processing circuit 210. Memory controller 230 may also beconfigured to abstract or otherwise manage certain aspects of memorymanagement from or for processing circuit 210. Although memorycontroller 230 is illustrated as single memory controller separate fromprocessing circuit 210, in other examples, multiple memory controllersmay be employed, memory controller(s) may be integrated with operatingmemory 220, or the like. Further, memory controller(s) may be integratedinto processing circuit 210. These and other variations are possible.

In computing device 200, data storage memory 250, input interface 260,output interface 270, and network adapter 280 are interfaced toprocessing circuit 210 by bus 240. Although, FIG. 2 illustrates bus 240as a single passive bus, other configurations, such as a collection ofbuses, a collection of point to point links, an input/output controller,a bridge, other interface circuitry, or any collection thereof may alsobe suitably employed for interfacing data storage memory 250, inputinterface 260, output interface 270, or network adapter 280 toprocessing circuit 210.

In computing device 200, data storage memory 250 is employed forlong-term non-volatile data storage. Data storage memory 250 may includeany of a variety of non-volatile data storage devices/components, suchas non-volatile memories, disks, disk drives, hard drives, solid-statedrives, or any other media that can be used for the non-volatile storageof information. However, data storage memory 250 specifically does notinclude or encompass communications media, any communications medium, orany signals per se. In contrast to operating memory 220, data storagememory 250 is employed by computing device 200 for non-volatilelong-term data storage, instead of for run-time data storage.

Also, computing device 200 may include or be coupled to any type ofprocessor-readable media such as processor-readable storage media (e.g.,operating memory 220 and data storage memory 250) and communicationmedia (e.g., communication signals and radio waves). While the termprocessor-readable storage media includes operating memory 220 and datastorage memory 250, the term “processor-readable storage media,”throughout the specification and the claims whether used in the singularor the plural, is defined herein so that the term “processor-readablestorage media” specifically excludes and does not encompasscommunications media, any communications medium, or any signals per se.However, the term “processor-readable storage media” does encompassprocessor cache, Random Access Memory (RAM), register memory, and/or thelike.

Computing device 200 also includes input interface 260, which may beconfigured to enable computing device 200 to receive input from users orfrom other devices. In addition, computing device 200 includes outputinterface 270, which may be configured to provide output from computingdevice 200. In one example, output interface 270 includes a framebuffer, graphics processor, graphics processor or accelerator, and isconfigured to render displays for presentation on a separate visualdisplay device (such as a monitor, projector, virtual computing clientcomputer, etc.). In another example, output interface 270 includes avisual display device and is configured to render and present displaysfor viewing.

In the illustrated example, computing device 200 is configured tocommunicate with other computing devices or entities via network adapter280. Network adapter 280 may include a wired network adapter, e.g., anEthernet adapter, a Token Ring adapter, or a Digital Subscriber Line(DSL) adapter. Network adapter 280 may also include a wireless networkadapter, for example, a Wi-Fi adapter, a Bluetooth adapter, a ZigBeeadapter, a Long-Term Evolution (LTE) adapter, or a 5G adapter.

Although computing device 200 is illustrated with certain componentsconfigured in a particular arrangement, these components and arrangementare merely one example of a computing device in which the technology maybe employed. In other examples, data storage memory 250, input interface260, output interface 270, or network adapter 280 may be directlycoupled to processing circuit 210, or be coupled to processing circuit210 via an input/output controller, a bridge, or other interfacecircuitry. Other variations of the technology are possible.

Some examples of computing device 200 include at least one memory (e.g.,operating memory 220) adapted to store run-time data and at least oneprocessor (e.g., processing unit 210) that is respectively adapted toexecute processor-executable code that, in response to execution,enables computing device 200 to perform actions. In some examples,computing device 200 is enabled to perform actions such as the actionsin the process of FIG. 4 below, or actions in a process performed by oneor more of the computing devices in FIG. 3 or FIG. 5 below.

Illustrative Systems

FIG. 3 is a block diagram illustrating an example of a system (300) forIoT data control. System 300 may include network 330, IoT hub 351, IoTdevices 341-343, gateway devices 311 and 312, and application back-end313, which all connect to network 330. The term “IoT device” refers to adevice intended to make use of IoT services. An IoT device can includevirtually any device that connects to the cloud to use IoT services,including for telemetry collection or any other purpose. Applicationback-end 313 refers to a device, or multiple devices such as adistributed system, that performs actions that enable data collection,storage, and/or actions to be taken based on the IoT data, includinguser access and control, data analysis, data display, control of datastorage, automatic actions taken based on the IoT data, and/or the like.Application back-end 313 could also be one or more virtual machinesdeployed in a public or private cloud. In some examples, at least someof the actions taken by the application back-end may be performed byapplications running in application back-end 313. The term “IoT hub”refers to a device, or multiple devices such as a distributed system, towhich, in some examples, IoT devices connect on the network for IoTservices. In some examples, the IoT hub is excluded, and IoT devicescommunicate with application back-end 313, directly or through one ormore intermediaries, without communicating with an IoT hub. Users of IoTdevices receive IoT services via communication with the IoT servicesolution. The IoT solution service may be, in various examples, the IoThub or the application back-end (e.g., the IoT solution service may be asoftware component in the application back-end). For instance, someexamples include IoT hub 351 and IoT hub 351 acts as the IoT solutionservice. In other examples, IoT hub 351 is excluded from system 300, andapplication backend 313 acts as the IoT solution service.

Each of the IoT devices 341-343, gateway devices 311 and 312, and/or thedevices that comprise IoT hub 351 and/or application back-end 313 mayinclude examples of computing device 200 of FIG. 2. The term “IoTsolution service” is not limited to one particular type of IoT service,but refers to the device to which the IoT device communicates, afterprovisioning, for at least one IoT solution or IoT service. That is, theterm “IoT solution service,” as used throughout the specification andthe claims, is generic to any IoT solution. FIG. 3 and the correspondingdescription of FIG. 3 in the specification illustrates an example systemfor illustrative purposes that does not limit the scope of thedisclosure.

Network 330 may include one or more computer networks, including wiredand/or wireless networks, where each network may be, for example, awireless network, local area network (LAN), a wide-area network (WAN),and/or a global network such as the Internet. On an interconnected setof LANs, including those based on differing architectures and protocols,a router acts as a link between LANs, enabling messages to be sent fromone to another. Also, communication links within LANs typically includetwisted wire pair or coaxial cable, while communication links betweennetworks may utilize analog telephone lines, full or fractionaldedicated digital lines including T1, T2, T3, and T4, IntegratedServices Digital Networks (ISDNs), Digital Subscriber Lines (DSLs),wireless links including satellite links, or other communications linksknown to those skilled in the art. Furthermore, remote computers andother related electronic devices could be remotely connected to eitherLANs or WANs via a modem and temporary telephone link. Network 330 mayinclude various other networks such as one or more networks using localnetwork protocols such as 6LoWPAN, ZigBee, or the like. Some IoT devicesmay be connected to a gateway device via a different network in network330 than other IoT devices. In essence, network 330 includes anycommunication method by which information may travel between IoT hub351, IoT devices 341-343, gateway devices 311 and 312, and applicationback-end 313. Although each device or service is shown connected asconnected to network 330, that does not mean that each devicecommunicates with each other device shown. In some examples, somedevices/services shown only communicate with some other devices/servicesshown via one or more intermediary devices. Also, other network 330 isillustrated as one network, in some examples, network 330 may insteadinclude multiple networks that may or may not be connected with eachother, with some of the devices shown communicating with each otherthrough one network of the multiple networks and other of the devicesshown communicating with each other with a different network of themultiple networks.

As one example, IoT devices 341-343 are devices that are intended tomake use of IoT services provided by the IoT solution service, which, insome examples, includes one or more IoT hubs, such as IoT hub 351.Application back-end 313 includes a device or multiple devices thatperform actions in providing a device portal to users of IoT devices.

Optional gateway devices 311-312 are devices that may be used by some ofthe IoT devices 341-343 for accessing IoT hub 351. In some examples,after provisioning, some or all of the IoT devices 341-343 communicateto IoT hub 351 without using an intermediary. In other examples, some orall of the IoT devices 341-343 communicate with IoT hub 351 using anintermediary device such as one or more of gateway devices 311-312.Application back-end 313 is a service which may be used by users of IoTdevices to manage IoT services for IoT devices including IoT device 341.

System 300 may include more or less devices than illustrated in FIG. 3,which is shown by way of example only.

Illustrative Processes

For clarity, the processes described herein are described in terms ofoperations performed in particular sequences by particular devices orcomponents of a system. However, it is noted that other processes arenot limited to the stated sequences, devices, or components. Forexample, certain acts may be performed in different sequences, inparallel, omitted, or may be supplemented by additional acts orfeatures, whether or not such sequences, parallelisms, acts, or featuresare described herein. Likewise, any of the technology described in thisdisclosure may be incorporated into the described processes or otherprocesses, whether or not that technology is specifically described inconjunction with a process. The disclosed processes may also beperformed on or by other devices, components, or systems, whether or notsuch devices, components, or systems are described herein. Theseprocesses may also be embodied in a variety of ways. For example, theymay be embodied on an article of manufacture, e.g., asprocessor-readable instructions stored in a processor-readable storagemedium or be performed as a computer-implemented process. As analternate example, these processes may be encoded asprocessor-executable instructions and transmitted via a communicationsmedium.

FIG. 4 is a logical flow diagram illustrating an example of a process(490) for IoT authentication. Some examples of the process are performedby an IoT solution service, such as IoT hub 351 of FIG. 3, or a softwarecomponent in application back-end 313 of FIG. 3. After a start block,the process proceeds to block 491. At block 491, a declarative telemetryrequest is received. The declarative telemetry request is a request fordata from multiple IoT devices. Although a declarative telemetry requestis specifically discussed, in some examples, other types of declarativeIoT data requests can also be made. In some examples, the declarativetelemetry request is sent to the IoT solution service from anapplication in the application back-end.

As examples of declarative IoT requests for illustrative purposes, oneexample declarative IoT telemetry request is a request to receive thetorque values of all turbines in a power plant. Another exampledeclarative IoT telemetry request is a request associated with obtainingdata used for displaying a dashboard showing the average of the sum ofoutput power produced in the power plant.

An application from the application back-end can make a declarative IoTdata request as if all of the device telemetry and other IoT data isavailable and ready to be routed in response to a declarative IoT datarequest, and such that it appears to the application that no buffering,batching, or the like is required. The declarative IoT data request is ahigh-level declarative description of the IoT data being requested. Thedeclarative request is a dynamic request in some examples. Thedeclarative IoT data request need not specify how the request isanswered, and in some examples the manner in which the request isanswered is de-coupled from the request itself.

In some examples, the IoT device code does not require functionalchanges, the application back-end does not require differentsolution-specific code or alteration of functional design, and/or thelike, depending on the type of IoT data being requested. Instead, theapplication back-end simply makes the request, de-coupled from themanner in which the request is answered. For instance, an exampledeclarative telemetry request may be a request for the temperature ineach room of a particular smart building, and the declarative telemetryrequests need not take into account which manufactures the temperaturesensors are from, even if the temperature sensors are from multipledifferent manufacturers, or have different firmware and/or software,different per-device sensor wiring, and/or the like. Further, thedeclarative telemetry request may be independent and/or agnostic of theparticularities of the sensors. In other words, the declarative IoT datarequest may be made without knowing or enforcing any schema upon thedevice telemetry.

The type of declarative IoT request made at step 491 depends on thefunction(s) being performed by the application. Telemetry and other datafrom IoT devices may be requested for a variety of different purposes,including, for example, raw telemetry, special events, diagnostictelemetry, hot path analytics, alerts, and archival of telemetry data.In some examples, one or more declarative IoT requests may be made inorder for an application to provide a visual dashboard of telemetrydata, such as via graphs or the like.

The process then moves to block 492. At block 492, the declarativetelemetry request is decomposed, converted, or otherwise translated intoa plurality of individual instructions or individual sets ofinstructions. In some examples, the individual instructions or sets ofinstructions correspond to individual configurations for IoT devices.The individual configurations may include configurations ofcorresponding edge devices (e.g., IoT devices and/or intermediarydevices) to configure the corresponding edge devices to send particulardata to the IoT solution service at a particular frequency. Theconfigurations may be coded to cause a device that executes theconfiguration to filter, buffer, compress, and/or send particular IoTdata, including to send particular IoT data at a particular frequency.

Some configurations may vary based on one or more factors. For example,configurations may configure the devices to selectively send telemetry.Some configurations may vary the rate at which the data is sent, basedon one or more factors, such as sending the data every five minutes ifthe device is on Wi-Fi, and every two hours otherwise. In some example,instead of only sending the data more frequently if the device is onWi-Fi, the data may also be sent more frequently if the device isprocessing location information in any manner, including over Wi-Fi orover cellular. Some declarative IoT requests may result in thetranslated individual instructions requesting a different frequency ofsending telemetry data than others. At step 492, the configurations maybe generated so that the devices are configured to send the telemetrydata to be used to suitably respond to the declarative IoT data requestsand at the frequency necessary to suitably respond to the declarativeIoT data requests.

The IoT solution service may take into account the connections betweendevices and gateways, as well as the capabilities of the devices fortranslating the declarative IoT data request into individualinstructions or sets of instructions, in some examples. For example,some of the devices may be able to do buffering, some of the devicemight not be able to do buffering, and the declarative IoT data requestis translated into individual instructions or sets of instructionsaccordingly.

The individual instructions or sets of instructions are optimized insome examples. For instance, in some examples, if one declarativerequest is for temperature every ten minutes, and another is fortemperature and humidity every ten minutes, the IoT solution service canmerge the requests and not request temperature twice. In some examples,part of the optimization may be achieved via hierarchical categories ofIoT devices that is part of metadata stored in the IoT solution servicefor the IoT devices. That is, IoT devices may divided hierarchicallyinto categories, which are further categorized into sub-categories, andso on, and these hierarchical categories may be taken into account inthe optimization. The declarative IoT requests may be translated intoinstructions in a multi-level manner based on multiple hierarchicallayers, in which the hierarchical categories to which IoT devices belongare updated automatically. In these examples, the stored metadataincludes hierarchical categorization of the IoT devices, and thetranslating of the declarative IoT request into the individualinstructions is based, in part, on the metadata.

The process then advances to block 493. At block 493, destination IoTdevices associated with the plurality of individual instructions may beidentified. In some examples, the devices that provide the data that isto be used to answer the request are identified at step 493. In oneexample, in order to respond to the declarative IoT data request, IoTdata is obtained—e.g., IoT data that is or was collected by one or moreIoT devices. In this example, the plurality of individual instructionsare instructions used to obtain the IoT data from the IoT devices. Also,in this example, each individual instruction has an associateddestination device to which the instruction is to be sent in order toobtain the IoT data. These destination devices are identified at step493. In some examples, the determination at step 493 may be made basedon metadata for the IoT devices stored in the IoT solution service. Forexample, a request may be made that requires gathering the temperaturedata from all temperature sensors in a particular smart building. Insome examples, the IoT solution service includes metadata for the IoTdevices that includes information about which devices are temperaturesensors and which devices are in the particular smart building. Thismetadata may be used to assist in identifying the destination IoTdevices at block 493. More information about particular example of theuse of metadata, including device twins in some examples, foridentifying destination IoT examples, is given in greater detail below.

The process then proceeds to block 494. At block 494, the instructionsare sent to the destination IoT devices, i.e., to the individual or setsof instructions are sent to the destination devices identified at block493 or to intermediary devices to which the destination IoT devicescommunicate the IoT data. In some examples, at block 494, the pluralityof individual instructions is communicated such that the individualinstructions are communicated to the edge devices that the individualinstructions or sets of instructions correspond to. In some examples,some or all of the IoT devices are configurable, and the individualinstructions or sets of instructions include configurations sent to theIoT devices themselves. In some examples, some or all of the IoT devicesare not configurable, e.g. such IoT devices may send all telemetry datato an intermediary device which may be configurable. In such examples,and the individual instructions or sets of instructions may includeconfigurations sent to the intermediary devices.

Although blocks 492-494 are shown as separate steps and in a particularorder, in some examples, one or more the steps are block 492-494 may beperformed in a different order than shown, or may be performed at thesame time. For instance, in some examples, the instructions aredecomposed while being propagated through the network.

In some examples, the intermediary devices are gateways such as fieldgateways that communicate with some of the IoT devices and with the IoTsolution service, and the intermediary devices are configurable inresponse to the configurations that are sent at step 494. In someexamples, the IoT devices send IoT data to the configurable intermediarydevice, and the configurable intermediary device is configured based onthe configuration to filter, buffer, compress, and/or send particularIoT data to the IoT solution service, including to send particular IoTdata to the IoT solution service at a particular configured frequency.

The process then moves to block 495. At block 495, telemetry data orother IoT data may be received from the destination IoT devices (viaintermediary devices in some examples) based on the plurality ofindividual instructions. As previously discussed, in some examples, theindividual instructions are configurations that may cause a deviceconfigured based on the configuration to filter, buffer, compress,and/or send particular IoT data, including to send particular IoT dataat a particular configured frequency. The destination IoT devices maythen send data based on the configuration, and the data sent by thedestination IoT devices is received at block 495. In some examples, atblock 495, IoT data is received from the corresponding edge devices uponthe edge devices being configured based on execution of theconfigurations on the corresponding edge devices, and the correspondingedge devices sending IoT data in accordance with the executedconfigurations.

The process then proceeds to block 496. At block 496, the declarativetelemetry request may be responded to by the IoT devices and/orintermediary devices based on the received telemetry data. In someexamples, once the IoT data to be used to respond to the declarative IoTrequest is received, the IoT solution service then answers the request,based on the received IoT data, according to the particular IoT datarequest. The process may then advance to a return block, where otherprocessing is resumed.

One example IoT device is a generator telematics unit that is capable ofproviding the following telemetry streams: engine hours, fuelconsumption, engine temperature, engine fluid level/pressure, vehicleelectrical power, electronic engine controller, and active diagnostictroubles codes. One example declarative IoT telemetry request is arequest to send some of the telemetry streams to a large compressed fileand to send the file to storage. Another example declarative IoTtelemetry request is a request to send the telemetry streams for runhours, fuel, and oil temperature to a dashboard every five minutes.Another example declarative IoT telemetry request is a request to routeall alerts based on the active diagnostic troubles codes to a criticalqueue.

Although not shown in FIG. 4, after step 496, in some examples, theconfigurations are updated. For instance, in some examples, after adevice is de-provisioned, the configuration for the de-provisioneddevice is updated according. If for example a device is moved from afirst power plant to a second power plant, then the IoT solution serviceupdates the configurations accordingly to reflect the change, and thensends the updated configurations. In some examples, the configurationsare updated based on metadata stored in the IoT solution service foreach device.

For instance, in some examples, if there are existing IoT telemetryrequests to obtain the temperature readings for all temperature sensorsin the first power plant, and a temperature sensor is moved from thefirst power plant to the second power plant, then the metadata fordevices stored in the IoT solution service is updated, and aconfiguration is sent to the device (or to a corresponding intermediarydevice) to now send temperature data. In some examples, the IoT solutionservice has metadata for each device which defines categories orproperties for each IoT device, with information such as location of thedevice and type of the device. In some examples, as previouslydiscussed, these categories are hierarchical, and are automaticallyupdated upon being applicable, such as upon a sensor being moved to adifferent building. In some examples, at least some of the metadata foreach IoT device is synchronized with the corresponding IoT deviceitself.

In some examples, the metadata stored in the IoT solution service forthe IoT devices is stored as in a logical “twins” of the devices. Inthese examples, the twins are the cloud representations of connecteddevices. In these examples, each twin has metadata regarding acorresponding IoT device. Each twin may include information about thecorresponding device such as the type of device it is, and variousproperties of the device, including capabilities of the device and theconfigurations that the device has executed. For instance, one exampletwin may indicate that the corresponding device is an uninterruptablepower supply, that the device has an associated IoT panel, and that thedevice has a battery level. At least a portion of the twin issynchronized with the corresponding IoT device in some examples. In someexamples, the twins are queryable, and can be used in the answering ofqueries including declarative IoT requests.

For example, an IoT declarative telemetry request made be in a form suchas, for example:

telemetryType = “temp” AND $device.tags.building = “B43” AND$device.tags.deviceType = “tempSensor” BUFFER_UNTIL 5m

In this example, the twins are queryable, which may be used to assistthe IoT solution service in determining which IoT devices have the tag“B43,” which IoT devices have the tag “tempSensor.”

Whether stored as twins or in some other manner, metadata that can bereferred to in the telemetry requests about the device may be stored inthe cloud, may be stored on the device, or in some combination thereof.

FIG. 5 is a block diagram illustrating an example of system 400, whichmay be employed as an example of system 300 of FIG. 3. System 500includes IoT devices 541-543, IoT hub 551, and application back-end 513.IoT hub 551 includes dispatcher 589. Application back-end 513 includesalert trigger component 581, archive component 582, and real-timedashboard and trigger rules component 583.

As shown in FIG. 5, an example IoT declarative telemetry request made bein a form such as, for example:

telemetryType = “temp” AND $device.tags.building = “B43” AND$device.tags.deviceType = “tempSensor” BUFFER_UNTIL 5m

This example IoT declarative request can be decomposed into two parts:

The set of devices that are to be requested to send telemetry in orderto respond to the request:

$device.tags.building=“B43” AND $device.tags.deviceType=“tempSensor”,and

The configuration of which telemetry to send:

telemetryType=“temp” BUFFER_UNTIL 5 m

Instead of assuming that devices send all messages to the cloud and theIoT solution service filters this immutable stream, the IoT solutionservice can use the same filter expression and configure the devices toonly send the determined telemetry.

The combination of filtering on both message properties and twinproperties may result in a very powerful language that allows solvingreal world scenarios such as a wireless device that is configured tosend telemetry every 5 minutes if it is on Wi-Fi, every hour if on ametered connection, and a device that sends logs every 24 hours, butimmediately if there is a critical error.

CONCLUSION

While the above Detailed Description describes certain examples of thetechnology, and describes the best mode contemplated, no matter howdetailed the above appears in text, the technology can be practiced inmany ways. Details may vary in implementation, while still beingencompassed by the technology described herein. As noted above,particular terminology used when describing certain features or aspectsof the technology should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects with which that terminology is associated. Ingeneral, the terms used in the following claims should not be construedto limit the technology to the specific examples disclosed herein,unless the Detailed Description explicitly defines such terms.Accordingly, the actual scope of the technology encompasses not only thedisclosed examples, but also all equivalent ways of practicing orimplementing the technology.

We claim:
 1. An apparatus for Internet of Things (IoT) data control,comprising: an IoT solution service, including: a memory adapted tostore run-time data for the IoT solution service; and at least oneprocessor that is adapted to store and execute processor-executable codethat, in response to execution, enables the IoT solution service toperform actions, including: receiving a declarative telemetry request,wherein the declarative telemetry request is a request for data frommultiple IoT devices; translating the declarative telemetry request intoa plurality of individual instructions; identifying destination IoTdevices associated with the plurality of individual instructions;sending the plurality of individual instructions; receiving telemetrydata from the destination IoT devices based on the plurality ofindividual instructions; and responding to the declarative telemetryrequest based on the received telemetry data.
 2. The apparatus of claim1, the actions further including: determining updated individualinstructions, and sending the updated individual instructions.
 3. Theapparatus of claim 1, wherein the declarative telemetry request isreceived from an application in an application back-end.
 4. Theapparatus of claim 1, wherein the individual instructions areconfigurations.
 5. The apparatus of claim 4, wherein the configurationsare coded to cause at least one of an IoT device or an intermediarydevice to send telemetry data at a configured frequency.
 6. Theapparatus of claim 1, the actions further including: storing metadatarelating to the IoT devices, wherein translating the declarativetelemetry request into a plurality of individual instructions is based,in part, on the metadata.
 7. The apparatus of claim 6, wherein thestored metadata includes hierarchical categorization of the IoT devices.8. The apparatus of claim 7, wherein the stored metadata includes devicetwins, wherein the device twins correspond to IoT devices, and wherein aportion of each device twin is synchronized with the corresponding IoTdevice such that the hierarchical categorization of the IoT devices isupdated automatically based on changes to the hierarchicalcategorization.
 9. The apparatus of 8, further comprising: determiningupdated individual instructions based on the automatic updating of thehierarchical categorization; and sending the updated individualinstructions.
 10. A method for Internet of Things (IoT) data control,comprising: receiving a declarative data request, wherein thedeclarative data request is a request for data from multiple IoTdevices; employing at least one processor to translate the declarativedata request into a plurality of individual requests; identifyingdestination IoT devices associated with the plurality of individualrequests; sending the plurality of individual requests; receiving IoTdata from the destination IoT devices based on the plurality ofindividual requests; and responding to the declarative data requestbased on the received IoT data.
 11. The method of claim 10, wherein thedeclarative data request is a declarative telemetry request, and whereinthe IoT data is telemetry data.
 12. The method of claim 10, furthercomprising: determining updated individual requests, and sending theupdated individual requests.
 13. The method of claim 10, wherein theindividual requests are configurations.
 14. The method of claim 13,wherein the configurations are coded to cause at least one of an IoTdevice or an intermediary device to send telemetry data at a configuredfrequency.
 15. The method of claim 10, further comprising: storingmetadata relating to the IoT devices, wherein translating thedeclarative telemetry request into the plurality of individual requestsis based, in part, on the metadata.
 16. The method of claim 15, whereinthe stored metadata includes hierarchical categorization of the IoTdevices.
 17. A processor-readable storage medium, having stored thereonprocess-executable code for computer network design, that, uponexecution by at least one processor, enables actions, comprising:decomposing a declarative data request into a plurality ofconfigurations such that the configurations are associated withcorresponding edge devices; communicating the plurality ofconfigurations such that the configurations are communicated to thecorresponding edge devices; receiving IoT data from the correspondingedge devices upon the edge devices being configured based on executionof the configurations on the corresponding edge devices and sending IoTdata in accordance with the executed configurations; and responding tothe declarative data request based on the received IoT data.
 18. Theprocessor-readable storage medium of claim 17, wherein the declarativedata request is a declarative telemetry request, and wherein the IoTdata is telemetry data.
 19. The processor-readable storage medium ofclaim 17, the actions further including: determining updatedconfigurations, and sending the updated configurations.
 20. Theprocessor-readable storage medium of claim 17, the actions furtherincluding: storing metadata relating to the IoT devices, whereindecomposing the declarative data request into the plurality ofconfigurations is based, in part, on the metadata.